Container mobility based on border gateway protocol prefixes

ABSTRACT

The disclosure describes systems and methods for minimizing latency for users accessing services hosted on a cloud-computing system. A device receives a request to deploy a compute container to provide services to a prefix. The device determines a first prefix-connection location of the prefix. The device deploys the compute container based on the first prefix-connection location. The device determines a second prefix-connection location of the prefix. The device determines that the second prefix-connection location is different from the first prefix-connection location. The device migrates the compute container based on the second prefix-connection location.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/532,924 filed on Nov. 22, 2021, entitled “CONTAINER MOBILITY BASED ONBORDER GATEWAY PROTOCOL PREFIXES,” which is a continuation of U.S.patent application Ser. No. 16/836,680 filed on Mar. 31, 2020, entitled“CONTAINER MOBILITY BASED ON BORDER GATEWAY PROTOCOL PREFIXES,” andwhich issued as U.S. Pat. No. 11,184,433 on Nov. 23, 2021. Theaforementioned applications are expressly incorporated herein byreference in their entirety.

BACKGROUND

A cloud-computing system may refer to a collection of computing devicesor resources that can be accessed remotely. Stated another way, cloudcomputing may be described as the delivery of computing services (suchas storage, databases, networking, software, applications, processing,or analytics) over the Internet. Clients may access a cloud-computingsystem through a client device. The cloud-computing system may includeresources that provide services to clients. These resources may includeprocessors, memory, storage, and networking hardware.

A cloud-computing system may include a number of data centers that maybe located in different geographic locations. Each data center mayinclude many servers. A server may be a physical computer system. Thecloud-computing system may run virtual machines on a server. A virtualmachine may be a program that emulates a distinct computer system butthat can run on a server with other virtual machines. Like a physicalcomputer, a virtual machine may include an operating system andapplications.

Data centers may be located far away from large population centers andfrom clients who access the cloud-computing system. The distance betweenthe client and the data center may cause a client to experience latencyin accessing the cloud-computing system.

SUMMARY

In some aspects, the techniques described herein relate to methods,systems, and computer program products, including: receiving a requestto deploy a compute container to provide services to a prefix;determining a first prefix-connection location of the prefix; deployingthe compute container based on the first prefix-connection location;determining a second prefix-connection location of the prefix;determining that the second prefix-connection location is different fromthe first prefix-connection location; and migrating the computecontainer based on the second prefix-connection location.

In some aspects, the techniques described herein relate to methods,systems, and computer program products, including: receiving a requestto deploy a compute container to provide services to a prefix;determining a first prefix-connection location of the prefix, wheretraffic from the prefix enters a cloud-computing system at a first time;deploying the compute container based on the first prefix-connectionlocation; determining a second prefix-connection location of the prefix,where traffic from the prefix enters the cloud-computing system at asecond time after the first time; determining that the secondprefix-connection location is different from the first prefix-connectionlocation; and migrating the compute container based on the secondprefix-connection location.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Additional features and advantages will be set forth in the descriptionthat follows. Features and advantages of the disclosure may be realizedand obtained by means of the systems and methods that are particularlypointed out in the appended claims. Features of the present disclosurewill become more fully apparent from the following description andappended claims, or may be learned by the practice of the disclosedsubject matter as set forth hereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and otherfeatures of the disclosure can be obtained, a more particulardescription will be rendered by reference to specific embodimentsthereof which are illustrated in the appended drawings. For betterunderstanding, the like elements have been designated by like referencenumbers throughout the various accompanying figures. Understanding thatthe drawings depict some example embodiments, the embodiments will bedescribed and explained with additional specificity and detail throughthe use of the accompanying drawings in which:

FIG. 1 illustrates an example cloud-computing system for minimizinglatency experienced by client devices accessing services of thecloud-computing system.

FIG. 2 illustrates an example service for minimizing latency experiencedby client devices accessing a cloud-computing system.

FIG. 3 illustrates an example of a cloud-computing system migrating acontainer based on changes to a prefix-connection location.

FIG. 4 illustrates an example method for migrating a container to a newlocation within a cloud-computing system.

FIG. 5 illustrates an example method for determining whether to move acontainer hosted within a cloud-computing system.

FIG. 6 illustrates an example method for migrating a compute containerbased on a prefix-connection location.

FIG. 7 illustrates an example method for sending messages to acloud-computing system.

FIG. 8 illustrates certain components that may be included in acomputing system.

DETAILED DESCRIPTION

This disclosure concerns systems and methods for reducing latency inaccessing dynamic content hosted on a cloud-computing system. Hostingdynamic content at an edge of the cloud-computing system may offerbetter latency profiles for compute-intensive and latency-sensitiveworkloads. In other words, the closer a container is to the user, thebetter the user experience is. But keeping a container close to the useris a challenge because the route traffic from the user travels to reachthe cloud-computing system may change. The systems and methods of thisdisclosure place dynamic content in containers hosted on edge sites ofthe cloud-computing system and automatically relocate the containersbased on where network traffic from a client device enters thecloud-computing system.

A cloud-computing system may refer to a collection of computing devicesor resources that can be accessed remotely. The cloud-computing systemmay provide computing services over the Internet to clients. Thecloud-computing system may host content provided by a third-partycontent provider and give customers of the content provider access tothe content. The cloud-computing system may include a number of datacenters located in different geographic locations. Each data center mayinclude multiple servers. A server may be a physical computer system.The server may include multiple virtual containers (such as virtualmachines). Each virtual container may provide services to a client. Inthis way, a single server may provide services to multiple clients. Avirtual container may provide a client access to content (such as agame) of a third-party content provider.

Data centers may be located far away from large population centers andfrom clients who access the cloud-computing system. Data centers may belarge real-estate complexes that require significant amounts of power tooperate. Land may be more available and less expensive in less populatedareas. Similarly, power may be cheaper and easier to access in lesspopulated areas. The distance between the client and the data center maycause a client to experience latency in accessing the cloud-computingsystem and services hosted on the cloud-computing system.

Clients who want to access cloud-computing services generally rely onone or more networks external to the cloud-computing system. The one ormore networks may include an internet service provider (ISP). It isunlikely that an ISP has, or that additional networks connecting the ISPto the cloud-computing system have, a large bandwidth to carry trafficto a data center located in a rural and potentially remote area. Thelimited bandwidth available for carrying traffic from a client device toa rural data center may result in a client experiencing latency inaccessing the cloud-computing system and receiving services from thecloud-computing system.

To help reduce latency a cloud-computing system may include edge sites.The edge sites may be part of the cloud-computing system and beconnected to the data center through the cloud-computing system'sinternal network and backbone. The edge sites may, however, be locatedcloser to where large groups of clients reside, such as in populationcenters and large cities. The edge sites may be able to receivecommunications from networks external to the cloud-computing system. Theedge sites may be much smaller in physical size than data centers. Theedge sites may also have much smaller capacity and fewer computingresources than data centers. As a result, the edge sites may be limitedto hosting frequently accessed content and services. But because edgesites may be located close to clients, hosting cloud-computing serviceson an edge site may reduce the latency a client experiences.Communications between the client and an edge site may have to travel ashorter distance than communications between the client and a datacenter. Moreover, an ISP may have more bandwidth available for carryingtraffic between a client and a nearby edge site than for carryingtraffic between a client and a distant data center.

Edge sites may also reduce latency and improve overall reliabilitybecause once information reaches an edge site, the cloud-computingsystem can use its own backbone and network to carry the information toa data center if necessary. The operator of a cloud-computing system maycontrol the reliability and bandwidth of the backbone and network of thecloud-computing system but have no control over the reliability ofnetworks external to the cloud-computing system. The operator of thecloud-computing system may have a greater incentive to maintain areliable network than those operating networks external to thecloud-computing system.

Reducing latency may improve user experience with the cloud-computingsystem and content (including third-party content) hosted on thecloud-computing system. For example, consider that a cloud-computingsystem hosts a software application (like a game) for a third-partycontent provider. Assume a user accesses the game using a smart phone.High latency may cause the game to constantly pause to load content. Orit may result in noticeable delays between performing actions on thesmart phone and the actions registering on the screen. Reducing thelatency may reduce or eliminate those delays, resulting in a muchsmoother game-playing experience for the user.

Improving user experience with third-party content hosted on thecloud-computing system may benefit the cloud-computing system operator.Third-party content providers may pay to host their content on thecloud-computing system. And the amount the third-party content providerpays may be based (at least in part) on the total demand for the contentprovider's content. When users have a good experience using thethird-party content provider's content on the cloud-computing system,demand for the content provider's content may increase. The increaseddemand may cause the content provider to pay more money to thecloud-computing system operator. Positive user experience with thecontent provider's content may also cause additional content providersto host their content on the cloud-computing system. Thus, reducinglatency may increase revenues of the cloud-computing system.

In addition to reducing latency, a cloud-computing system may attractcontent providers (which may also be referred to as service providers)by providing serverless computing. A cloud-computing system may providea physical server to a third-party service provider for hosting thethird-party's services. But because of the challenges with managing aphysical host, the cloud-computing system may also allow the serviceprovider to provide content using a virtual machine. A virtual machinemay be a program that emulates a distinct computer system but that canrun on a server with other virtual machines. Like a physical computer, avirtual machine may include an operating system and applications. Thus,managing the virtual machine is less complex than managing a server. Andusing virtual machines (rather than entire servers) gives the serviceprovider greater flexibility in choosing the amount of computingresources that it needs. But the service provider must still manage thevirtual machine (such as scaling the virtual machine as demandincreases). An even more flexible and less burdensome option (at leastfrom the service provider's perspective) is serverless computing. Withserverless computing, the service provider provides a cloud-computingsystem with small functions that together provide the service provider'sservices. The cloud-computing system then deploys the services in asandbox environment. The sandbox environment may host containers, whichprovide the service provider's services to customers. All the serviceprovider does is provide code. The operator of the cloud-computingsystem manages scaling and updating.

A cloud-computing system may improve customer and service providerexperience with the cloud-computing system by hosting serverlesscomputing containers on edge sites close to a user and dynamicallymigrating those containers in response to changes in where externaltraffic enters the cloud-computing system. Doing so may reduce latencyexperienced by users of services hosted on a cloud-computing system.

A service provider may provide content or code to a cloud-computingsystem operator. The operator may deploy the code in a container hostedat a data center. But because the data center may not be close to a userof the container, the cloud-computing system may automatically move thecontainer to minimize latency experienced by the user. For example, thecloud-computing system may automatically move the container to alocation within the cloud-computing system that is closer to the userthan the data center, such as an edge site near the user. The edge sitemay be where the user connects to the cloud-computing system. Or theedge site may be near where the user connects to the cloud-computingsystem if where the user connects to the cloud-computing system lackscapacity for the container. In the alternative to deploying thecontainer first at the data center and then migrating the container, thecloud-computing system may automatically deploy the container in thefirst instance near the user. In this context, a distance may bemeasured in terms of a physical distance or in terms of a distance asignal must travel from one point to another.

At some future point, the location (such as the edge site) hosting thecontainer may no longer be where traffic from the user enters thecloud-computing system. For example, the user may use an ISP to connectto the internet. The ISP may route traffic from the user to a secondnetwork, which then sends the traffic to a first edge site close to theuser. The first edge site may host a container that provides services tothe user. But the second network may become unavailable due tomaintenance, failure, cost, or other reasons. At that point, the ISP mayroute traffic to a third network, which then sends the traffic to asecond edge site farther from the user than the first edge site. Theuser's traffic now enters the cloud-computing system at the second edgesite, but the container that services the user is still at the firstedge site. In that situation, traffic from the user may have to travelthrough the cloud-computing system from the second edge site to thefirst edge site. This pathway may be long (and much longer than thepathway from the user to the second edge site) and result in asignificant increase in latency experienced by the user. The user, ofcourse, will not understand the cause of the latency increase and mayblame the service provider or the cloud-computing system.

To improve user experience the cloud-computing system may include aservice that automatically works to minimize latency based on changes innetwork routing. The service may automatically detect that the user'straffic now enters the cloud-computing system through the second edgesite. In response, the service may automatically migrate the containerfrom its current location to a new location closer to the second edgesite, such as at the second edge site. Because the second edge site isthe point where the user connects to the cloud-computing system, theuser experiences less latency.

To detect changes in where user traffic enters the cloud-computingsystem the service may periodically (such as at fixed time intervals)query edge sites for information regarding containers hosted at the edgesites. For each container, the service may create a record associatingthe container, an external network being serviced by the container, anda connection location where traffic from the external network isentering the cloud-computing system. At the next query, the service may,for each container, compare a current connection location of theexternal network with the previous connection location of the externalnetwork. If the current connection location is different from theprevious connection location, the service may migrate the container tothe current connection location. Automatically detecting changes inwhere traffic enters the cloud-computing system and automaticallymigrating containers in response to those changes improves userexperience with services hosted on the cloud-computing system. That inturn increases service-provider satisfaction and attracts more serviceproviders to the cloud-computing system. In at least this way, thedisclosed systems and methods improve cloud-computing technology.

FIG. 1 illustrates an example cloud-computing system 100 for reducinglatency in accessing cloud-computing services.

The cloud-computing system 100 may include a data center 102. The datacenter 102 may be a large real-estate complex that includes servers 104(e.g., server 104 a, server 104 b, server 104 c). The servers 104 mayinclude physical computing resources such as processors, memory,storage, and networking hardware. The data center 102 may require largeamounts of power to run the servers 104. The cloud-computing system 100may use the data center 102 to provide cloud-computing services toclients. The data center 102 may host content and services fromthird-party content and service providers.

The data center 102 may have a physical location. The physical locationof the data center 102 may be chosen based on land availability, landprices, access to power, power prices, ambient temperature, windconditions, etc. The physical location of the data center 102 may be faraway from large population centers. For example, the data center 102 maybe located in a remote, rural area.

The cloud-computing system 100 may include edge sites 106. The edgesites 106 may include physical computing resources. The edge sites 106may receive communications from networks external to the cloud-computingsystem 100. The physical computing resources of the edge sites 106 maybe more limited than the physical computing resources of the data center102. The edge sites 106 may be designed to store frequently accessedcontent or to provide frequently requested services. For example, assumethe cloud-computing system 100 stores digital copies of movies for acontent provider. Assume the edge sites 106 do not have enough storageto store all the movies hosted by the cloud-computing system 100. Assumethat the content provider uploads a new movie to the cloud-computingsystem 100 and that the content provider anticipates that the new moviewill be extremely popular. The cloud-computing system 100 may placecopies of the new movie on the edge sites 106.

The edge sites 106 may have physical locations different from the datacenter 102. The edge sites 106 may communicate with the data center 102through a network of the cloud-computing system 100. The edge site 106 amay have a first physical location and the edge site 106 b may have asecond physical location. The first physical location may be differentfrom the second physical location. The first physical location and thesecond physical location may be different from the physical location ofthe data center 102. The first physical location and the second physicallocation may be far away from the physical location of the data center102. The first physical location and the second physical location may bechosen to reduce a distance between clients who want to access servicesprovided by the cloud-computing system 100 and the physical computingresources of the cloud-computing system 100 that provide the services.Having a shorter physical distance between the clients and the edgesites 106 may mean that communications from the clients can reach theedge sites 106 much faster than the communications can reach the datacenter 102. The first physical location and the second physical locationmay be in large population centers. For example, the first physicallocation may be in a metropolitan area (such as Los Angeles, Calif.,USA), the second physical location may be in a different metropolitanarea (such as San Francisco, Calif., USA), and the data center 102 maybe in a rural area of West Virginia, USA. A communication from a clientin San Jose, Calif., USA may be able to reach either Los Angeles or SanFrancisco much faster than the communication can reach West Virginia.

Placing the edge sites 106 in metropolitan areas may reduce latencyexperienced by clients who access the cloud-computing system 100. Forexample, consider a situation where a client in Los Angeles, Calif.wants to use an app on the client's phone to view a movie that is storedon the cloud-computing system 100. Assume that the data center 102 islocated in West Virginia and the movie is stored on the data center 102.The large distance between the client and the data center 102 may resultin the client experiencing a slow response time between clicking on themovie in the app and the movie beginning playing on the phone. The largedistance may also cause pauses in the movie to allow for contentbuffering. But assume an alternative situation where a copy of the movieis stored on the edge site 106 a, and the edge site 106 a is located inLos Angeles. The shorter distance between the client and the edge site106 a may result in the client experiencing a faster response time thanthe client experienced when the movie was stored on the data center 102.

A client device 112 may access the cloud-computing system 100.Communications between the client device 112 and the cloud-computingsystem 100 may travel through one or more networks 114. The networks 114may be internet service providers. There may be connections 116 thatlink the client device 112, the networks 114, and the cloud-computingsystem 100. The connection 116 a may be a pathway through which theclient device 112 and the network 114 a can exchange information. Theconnection 116 b may be a pathway through which the network 114 a andthe network 114 b exchange information. The connection 116 c may be apathway through which the network 114 a and the network 114 c exchangeinformation. The connection 116 d may be a pathway through which thenetwork 114 b and the cloud-computing system 100 exchange information.To exchange information with the cloud-computing system 100 the network114 b may exchange information with the edge site 106 a. The connection116 e may be a pathway through which the network 114 c and thecloud-computing system 100 exchange information. To exchange informationwith the cloud-computing system 100 the network 114 c may exchangeinformation with the edge site 106 b. It may be that the network 114 adoes not have a connection through which it can exchange informationdirectly with the cloud-computing system 100.

There may be more than one pathway through which information can travelfrom the client device 112 to the cloud-computing system 100. A firstpathway may be the following: (a) the client device 112 sends data tothe network 114 a using the connection 116 a; (b) the network 114 asends the data to the network 114 b using the connection 116 b; and (c)the network 114 b sends the data to the edge site 106 a using theconnection 116 d. A second pathway may be the following: (a) the clientdevice 112 sends data to the network 114 a using the connection 116 a;(b) the network 114 a sends the data to the network 114 c using theconnection 116 c; and (c) the network 114 c sends the data to the edgesite 106 b using the connection 116 e.

One of the first pathway or the second pathway may be a primary pathwayand the other may be a secondary pathway. The network 114 a may senddata to the cloud-computing system 100 using the primary pathway unlessthe primary pathway is not available. When the primary pathway is notavailable, the network 114 a may send the data to the cloud-computingsystem 100 using the secondary pathway. A pathway may become unavailableif one or more connections or networks on the pathway becomeunavailable. A connection or network may become unavailable due to ahardware failure, due to the network or the connection refusing to carrytraffic for the cloud-computing system 100, or due to other reasons. Forexample, assume the primary pathway is the first pathway describedabove. Assume, however, that the network 114 b fails or goes down formaintenance. In that instance, the client device 112 and thecloud-computing system 100 may use the second pathway described above tocommunicate.

The primary pathway for transmitting data between the cloud-computingsystem 100 and the client device 112 may change. For example, the firstpathway may initially be set as the primary pathway, and thecloud-computing system 100 and the client device 112 may initiallyexchange information using the first pathway. At a later time, thesecond pathway may become the primary pathway. At that time, thecloud-computing system 100 and the client device 112 may exchangeinformation using the second pathway unless it becomes unavailable. Theprimary pathway may change for a variety of reasons. For example, assumethe first pathway described above is initially the primary pathway. Butassume the network 114 b increases prices for carrying traffic to thecloud-computing system 100. That may result in the second pathwaydescribed above becoming the primary pathway. In that situation, eventhough the first pathway is still available, the cloud-computing system100 and the client device 112 may stop using the first pathway and beginusing the second pathway to communicate.

The network 114 a may advertise one or more border gateway protocol(BGP) prefixes, which may be referred to as “prefixes.” A prefix may bea string of characters that indicates a source of network traffic. Aprefix may represent a collection of Internet Protocol (IP) addresses.One or more users may be behind a prefix. A prefix may indicate to thecloud-computing system 100 a network location for sending returncommunications. The network 114 a may advertise a prefix that includesthe client device 112. The cloud-computing system 100 may receive theprefix when the cloud-computing system receives communications from thenetwork 114 a that originate from the prefix. The network 114 a mayadvertise more than one prefix.

The edge sites 106 may include containers, such as container 108.Although FIG. 1 shows only the container 108, the edge site 106 a andthe edge site 106 b may contain multiple containers. The data center 102may also include containers.

The container 108 may be hosted in a compute sandbox deployed on theedge site 106 a. The container 108 may enable serverless computing. Thecompute sandbox may host multiple containers. The container 108 mayprovide access to computing resources, applications, content, orservices. The content provided by the container 108 may be static ordynamic. When the content is dynamic content, the container 108 maymaintain information about one or more states of the dynamic content.The container 108 may have a globally unique identifier (GUI) thatuniquely identifies the container 108 as compared to all othercontainers operating within the cloud-computing system 100. Thecontainer 108 may provide services to a particular client or clientdevice. The container 108 may be limited to providing services to theparticular client or client device. The container 108 may have acontainer location. The container location may be a location within thecloud-computing system 100 where the container 108 is hosted. Forexample, the container location of the container 108 may be the edgesite 106 a.

The container 108 may be associated with a prefix. Being associated witha prefix may mean the container 108 provides services to a useraccessing the cloud-computing system 100 from the prefix. The container108 may be associated with only a single prefix. The single prefix may,however, have multiple associated containers. Traffic from the prefixassociated with the container 108 may enter the cloud-computing system100. The traffic may enter the cloud-computing system 100 through anedge site, such as the edge site 106 a or the edge site 106 b. Trafficfrom the prefix associated with the container 108 may enter thecloud-computing system 100 at an edge site where the container 108 ishosted or at a different edge site. Traffic from the prefix associatedwith the container 108 may also enter the cloud-computing system 100 atthe data center 102.

The cloud-computing system 100 may include a service 110. The service110 may obtain BGP routes from all the edge sites 106. The BGP routesmay indicate a path (such as networks and connections) that dataentering the cloud-computing system 100 has taken to reach thecloud-computing system 100. The BGP routes may include prefixes. Anetwork being used by client devices to access the internet mayadvertise one or more prefixes to the cloud-computing system 100. Thecloud-computing system 100 may use the prefix to send data back to thenetwork and the client devices.

The service 110 may periodically obtain and store information regardingnetwork traffic at the edge sites 106. The service 110 may query one ormore of the edge sites 106 a, 106 b of the cloud-computing system 100for information regarding prefixes that are entering the cloud-computingsystem 100. The service 110 may store information regarding prefixesthat are entering the cloud-computing system 100. The service 110 mayalso obtain and store information regarding any containers that supportthe prefixes that are entering the cloud-computing system 100. Theservice 110 may associate the edge site where a prefix is entering thecloud-computing system 100, the prefix, and the containers that supportthe prefix in a record and store the record. For example, assume a firstprefix accesses the cloud-computing system 100 at the edge site 106 a.Also assume the container 108 provides services to the first prefix. Theservice 110 may associate, in a record, the edge site 106 a with thefirst prefix and the container 108. The service 110 may store the recordon the cloud-computing system 100.

The service 110 may periodically obtain and store information regardingcontainers (such as the container 108) operating on the edge sites 106.The service 110 may obtain the information at defined time intervals(such as every five minutes or every 30 seconds). The service 110 mayobtain and store the GUI for the container 108. The service 110 mayobtain and store information regarding the prefix the container 108supports. The service 110 may obtain and store information regarding aprefix-connection location for the prefix that the container 108supports. The prefix-connection location may be a location where trafficfrom the prefix enters the cloud-computing system 100. For example,assume the client device 112 accesses the network 114 a through a clientprefix. Assume that traffic from the client prefix is routed through thenetwork 114 b to the edge site 106 a. The prefix-connection location forthe client prefix may be the edge site 106 a. The service 110 mayassociate the GUI of the container 108 and the prefix the container 108supports. The service 110 may also associate the prefix-connectionlocation of the prefix associated with the container 108 with the GUI ofthe container 108 and the prefix. The service 110 may obtain and storeinformation about a container location of the container 108. The service110 may associate the container location (such as the edge site 106 a)with the GUI of the container 108.

The service 110 may use information the service 110 obtains regardingcontainers and prefixes to automatically determine whether to modifycontainer locations for containers hosted on the cloud-computing system100. The service 110 may use the information the service 110 obtains toautomatically determine how to modify the container locations. Theservice 110 may automatically determine how to modify the containerlocations based on the information the service 110 obtains.

For example, the service 110 may compare current information regardingcontainers operating on the edge sites 106 with past informationregarding containers operating on the edge sites 106. The service 110may, based on the comparison, automatically modify a location of one ormore containers operating in the cloud-computing system 100. The service110 may automatically modify the location of the one or more containersto reduce latency experienced by one or more users. The service 110 mayautomatically modify the location of the one or more containers suchthat the one or more containers are closer to where traffic fromprefixes supported by the one or more containers enters thecloud-computing system 100 than the containers are currently. In thiscontext, a first location may be closer to a second location than to athird location if data travels a shorter distance to go from the firstlocation to the second location than from the first location to thethird location. The service 110 may automatically migrate the one ormore containers to an edge site of the cloud-computing system 100 wherethe traffic supported by the one or more containers enters thecloud-computing system 100.

Consider the following example. At time t₀ the service 110 obtains andstores information regarding the container 108. The container 108 has aGUI of “4172ee21-fc66-44d8-be64-4c6b4db86870.” The container 108supports a prefix “50.1.1.0/24.” The prefix 50.1.1.0/24 has aprefix-connection location of the edge site 106 a. The service 110stores and associates the GUI, the prefix, and the prefix-connectionlocation as (4172ee21-fc66-44d8-be64-4c6b4db86870, 50.1.1.0/24, the edgesite 106 a). Now assume at time t₁, which is some period after time t₀,the service 110 again obtains information regarding the container 108.The container 108 has the GUI of 4172ee21-fc66-44d8-be64-4c6b4db86870and supports the prefix 50.1.1.0/24. But the prefix-connection locationof the prefix 50.1.1.0/24 is now edge site 106 b. The service 110 mayobserve that the prefix-connection location for the container 108 andthe prefix 50.1.1.0/24 at time t₀ is different from theprefix-connection location at time t₁. The service 110 may, in responseto that observation, determine to modify a container location of thecontainer 108. The service 110 may, based on that observation, migratethe container 108 to the prefix-connection location at time t₁, which isthe edge site 106 b.

In the above example, moving the container 108 from the edge site 106 ato the edge site 106 b may reduce latency experienced by a useraccessing dynamic content housed in the container 108. The followingexample illustrates this point. A user is located in Los Angeles,Calif., USA. The user uses the client device 112 to play an interactivegame hosted on the cloud-computing system 100. The edge site 106 a hoststhe interactive game (or at least some portion of the interactive game)for the user in the container 108. The user connects to the network 114a through the connection 116 a to play the interactive game. Trafficfrom the client device 112 travels through the connection 116 b, thenetwork 114 b, and the connection 116 d to the edge site 106 a. The edgesite 106 a is located within 100 miles of the user. After the user hasbeen playing the interactive game for a period of time whileexperiencing low latency, the network 114 b stops carrying traffic fromthe network 114 a to the edge site 106 a. At that time, traffic from thenetwork 114 a begins travelling through the network 114 c to the edgesite 106 b. The edge site 106 b is 500 miles from the user. Moreover,the edge site 106 b communicates with the edge site 106 a through thedata center 102. The data center 102 is located 1,000 miles from theedge site 106 a and the edge site 106 b. Even though the container 108is still within 100 miles of the client device 112, communications fromthe client device 112 may have to travel more than 2,500 miles to reachthe container 108. As a result, the user may experience significantlyhigher latency while playing the interactive game. Moving the container108 to the edge site 106 b means that communications from the clientdevice 112 to the container 108 have to travel only 500 miles (insteadof 2,500). That may reduce the latency the user experiences in playingthe interactive game.

FIG. 2 illustrates an example of a service 210 within a cloud-computingsystem 200.

The cloud-computing system 200 may provide services to client devices.The cloud-computing system 200 may provide services to the clientdevices on behalf of third-party content providers. To send data to thecloud-computing system 200 the client devices may connect to one or morenetworks external to the cloud-computing system 200. The networks mayannounce prefixes that represent the client devices.

Traffic from the prefixes may enter the cloud-computing system 200 at anedge site of the cloud-computing system 200. The cloud-computing system200 may include multiple edge sites. For example, the cloud-computingsystem 200 may include edge site 206 a, edge site 206 b, edge site 206c, and edge site 206 d. Traffic from prefix 218 a may enter thecloud-computing system 200 at the edge site 206 a. Traffic from prefix218 b may enter the cloud-computing system 200 at the edge site 206 b.Traffic from prefix 218 c may enter the cloud-computing system 200 atthe edge site 206 c. The cloud-computing system 200 may also includedata center 202.

The cloud-computing system 200 may provide services using containers.The cloud-computing system 200 may host containers at differentlocations within the cloud-computing system 200. The data center 202 mayhost container 208 e, the edge site 206 a may host container 208 a andcontainer 208 b, the edge site 206 c may host container 208 c, and theedge site 206 d may host container 208 d. A container may provideservices to a user associated with a prefix. For example, the container208 a may provide services to a first user accessing the cloud-computingsystem 200 from the prefix 218 a. The container 208 b may provideservices to a second user accessing the cloud-computing system 100 fromthe prefix 218 a. The container 208 c may provide services to a thirduser accessing the cloud-computing system 200 from the prefix 218 c. Thecontainer 208 d may provide services to a fourth user accessing thecloud-computing system 200 from the prefix 218 c. The container 208 emay provide services to a fifth user accessing the cloud-computingsystem 200 from the prefix 218 b.

The service 210 may obtain and store information regarding thecontainers 208 operating on the cloud-computing system 200. The service210 may obtain information regarding the containers 208 from the edgesites 206 and the data center 202. The service 210 may create and storea record 220 with the information regarding the containers. For example,the service 210 may obtain information regarding the container 208 a.The service 210 may obtain a GUI 222 a for the container 208 a. Theservice 210 may determine that the container 208 a is supporting theprefix 218 a. The service 210 may determine that the prefix 218 a isaccessing the cloud-computing system 200 at the edge site 206 a. Theservice 210 may associate the GUI 222 a, the prefix 218 a, and the edgesite 206 a in entry 220 a of the record 220. The service 210 may alsodetermine a container location for the container 208 a and include thecontainer location in the entry 220 a.

Similarly, the service 210 may obtain information regarding thecontainer 208 b. The service 210 may obtain a GUI 222 b for thecontainer 208 b. The service 210 may determine that the container 208 bis supporting the prefix 218 a. The service 210 may determine that theprefix 218 a is accessing the cloud-computing system 200 at the edgesite 206 a. The service 210 may associate the GUI 222 b, the prefix 218a, and the edge site 206 a in entry 220 b of the record 220. The servicemay also determine a container location for the container 208 b andinclude the container location in the entry 220 b.

Similarly, the service 210 may obtain information regarding thecontainer 208 c. The service 210 may obtain a GUI 222 c for thecontainer 208 c. The service 210 may determine that the container 208 cis supporting the prefix 218 c. The service 210 may determine that theprefix 218 c is accessing the cloud-computing system 200 at the edgesite 206 c. The service 210 may associate the GUI 222 c, the prefix 218c, and the edge site 206 c in entry 220 c of the record 220. The servicemay also determine a container location for the container 208 c andinclude the container location in the entry 220 c.

Similarly, the service 210 may obtain information regarding thecontainer 208 d. The service 210 may obtain a GUI 222 d for thecontainer 208 d. The service 210 may determine that the container 208 dis supporting the prefix 218 c. The service 210 may determine that theprefix 218 c is accessing the cloud-computing system 200 at the edgesite 206 c. The service 210 may associate the GUI 222 d, the prefix 218c, and the edge site 206 c in entry 220 d of the record 220. The servicemay also determine a container location for the container 208 d andinclude the container location in the entry 220 d.

Similarly, the service 210 may obtain information regarding thecontainer 208 e. The service 210 may obtain a GUI 222 e for thecontainer 208 e. The service 210 may determine that the container 208 eis supporting the prefix 218 b. The service 210 may determine that theprefix 218 b is accessing the cloud-computing system 200 at the edgesite 206 b. The service 210 may associate the GUI 222 e, the prefix 218b, and the edge site 206 b in entry 220 e of the record 220. The servicemay also determine a container location for the container 208 e andinclude the container location in the entry 220 e.

The service 210 may use the information the service 210 obtainsregarding the containers to determine whether to modify a location ofthe containers 208 hosted on the cloud-computing system 200. The service210 may modify the location of the containers 208 based on theinformation. The service 210 may determine a new location for thecontainers 208 based on the information. The service 210 may migrate oneor more of the containers 208 to new locations in order to reducelatency experienced by users. The service 210 may migrate one or more ofthe containers 208 to new locations closer to where traffic from theprefixes supported by the containers enter the cloud-computing system200. The service 210 may migrate one or more of the containers 208 toedge sites where the traffic from the prefixes supported by thecontainers enters the cloud-computing system 200.

In determining whether to modify the location of the containers 208, theservice 210 may compare current prefix-connection locations associatedwith the containers 208 a, 208 b, 208 c, 208 d, 208 e to previousprefix-connection locations associated with the containers 208 a, 208 b,208 c, 208 d, 208 e. The service 210 may determine to modify thelocation of a container if the current prefix-connection locationassociated with the container is different from the previousprefix-connection location associated with the container. In that case,the service 210 may migrate the container to a location closer to thecurrent prefix-connection location, such as the currentprefix-connection location. For example, assume the prefix 218 b (whichis associated with the container 208 e) has a previous prefix-connectionlocation of the data center 202. The current prefix-connection locationof the prefix 218 b is the edge site 206 b. The service 210 may observethat the previous prefix-connection location of the prefix 218 b isdifferent from the current prefix-connection location of the prefix 218b. In response to that observation, the service 210 may move thecontainer 208 e to the current prefix-connection location of the prefix218 b.

In determining whether to modify the location of the containers 208, theservice 210 may determine whether a first distance between the currentprefix-connection locations associated with the containers 208 and thecontainer locations of the containers is greater than a second distancebetween the previous prefix-connection locations associated with thecontainers 208 and the container locations of the containers. Thedistance at issue may be a measure of a distance a signal must travel.In the alternative, the distance may be a measure of time (such as anaverage time) it takes signals to travel from one location to another.The service 210 may determine to modify a container location if thefirst distance is greater than the second distance. In that case, theservice 210 may migrate the container to a location closer to thecurrent prefix-connection location, such as the currentprefix-connection location.

In determining whether to modify the location of the containers 208, theservice 210 may compare the prefix-connection location associated withthe containers 208 a, 208 b, 208 c, 208 d, 208 e with the containerlocations associated with the containers 208 a, 208 b, 208 c, 208 d, 208e. The service 210 may determine to modify the location of a containerif the prefix-connection location associated with the container isdifferent from the container location. In that case, the service 210 maymigrate the container to a location closer to the prefix-connectionlocation, such as the prefix-connection location. For example, thecontainer 208 d supports the prefix 218 c. The container location of thecontainer 208 d is the edge site 206 d. But the prefix-connectionlocation of the prefix 218 c is the edge site 206 c. The service 210 mayobserve that the container location of the container 208 d is differentfrom the prefix-connection location of the prefix 218 c. In response tothat observation, the service 210 may move the container 208 d to theedge site 206 c.

FIG. 3 illustrates an example timeline showing changes in acloud-computing system. FIG. 3 illustrates the cloud computing system atthree different points in time: to (shown as cloud-computing system 300a), t₁ (shown as cloud-computing system 300 b), and t₂ (shown ascloud-computing system 300 c). Time to occurs before time t₁, and timet₁, occurs before time t₂. The cloud-computing system 300 a, thecloud-computing system 300 b, and the cloud-computing system 300 c (andelements included therein) are intended to represent the samecloud-computing system but at different points in time.

At time t₀, the cloud-computing system 300 a includes edge site 306 a-1and edge site 306 a-2. The cloud-computing system 300 a includes service310 a. The edge site 306 a-1 hosts container 308 a. Prefix 318 a entersthe cloud-computing system 300 a at the edge site 306 a-1. The container308 a may provide services to a device behind the prefix 318 a.

At time t₀, the service 310 a may query the edge sites 306 a-1, 306 a-2for information regarding containers hosted on the edge sites 306 a-1,306 a-2. The service 310 a may query the edge site 306 a-1 to provideinformation regarding any containers hosted on the edge site 306 a-1.The edge site 306 a-1 may identify the container 308 a. For example, theedge site 306 a-1 may identify the container 308 a using a GUI of thecontainer 308 a. The edge site 306 a-1 may indicate that the container308 a provides services to the prefix 318 a. The edge site 306 a-1 mayindicate that the prefix 318 a is communicating with the edge site 306a-1. The service 310 a may store information identifying the container308 a, the prefix 318 a, a prefix-connection location for the prefix 318a (the edge site 306 a-1), and a container location of the container 308a (the edge site 306 a-1) as a record 320 a.

At time t₁, the cloud-computing system 300 b includes edge site 306 b-1and edge site 306 b-2. The cloud-computing system 300 b includes service310 b. The edge site 306 b-1 still hosts container 308 b. But prefix 318b now enters the cloud-computing system 300 b at the edge site 306 b-2.The container 308 b may still provide services to a device behind theprefix 318 b.

At time t₁, the service 310 b may again query the edge sites 306 b-1,306 b-2 for information regarding containers hosted on the edge sites306 b-1, 306 b-2. The service 310 b may query the edge site 306 b-1 toprovide information regarding any containers hosted on the edge site 306b-1. The edge site 306 b-1 may identify the container 308 b. Forexample, the edge site 306 b-1 may identify the container 308 b using aGUI of the container 308 b. The edge site 306 b-1 may indicate that thecontainer 308 b provides services to the prefix 318 b. The edge site 306b-1 may not, however, have information regarding where traffic from theprefix 318 a enters the cloud-computing system 300 b. The service 310 bmay learn that traffic from the prefix 318 b enters the cloud-computingsystem 300 b through the edge site 306 b-2 when the service 310 bqueries the edge site 306 b-2. The service 310 b may store informationidentifying the container 308 b, the prefix 318 b, a prefix-connectionlocation for the prefix 318 b (the edge site 306 b-2), and a containerlocation of the container 308 b (the edge site 306 b-1) as a record 320b.

The service 310 b may detect whether the prefix-connection locationassociated with the container 308 b has changed. The service 310 b maycompare the prefix-connection location in the record 320 b with theprefix-connection location in the record 320 a. The service 310 b maydetermine that the prefix-connection location shown in the record 320 bis different from the prefix-connection location shown in the record 320a.

The service 310 b may determine whether to modify a location of thecontainer 308 b based on whether the service 310 b detected that theprefix-connection location associated with the container 308 b haschanged. The service 310 b may determine to modify the location if theprefix-connection location has changed. In response to detecting achange, the service 310 b may determine to move the container 308 b fromthe edge site 306 b-1 to the edge site 306 b-2.

In the alternative, the service 310 b may determine whether to modify alocation of the container 308 b based on whether the container locationof the container 308 b in the record 320 b is different from theprefix-connection location shown in the record 320 b. The service 310 bmay compare the container location of the container 308 b in the record320 b with the prefix-connection location shown in the record 320 b. Theservice 310 b may determine to modify the location of the container 308b if the prefix-connection location shown in the record 320 b isdifferent from the container location shown in the record 320 b. Inresponse to that observation, the service 310 b may determine to movethe container 308 b from the edge site 306 b-1 to the edge site 306 b-2.

At time t₂, the cloud-computing system 300 c includes edge site 306 c-1and edge site 306 c-2. The cloud-computing system 300 c includes service310 c. The edge site 306 c-1 no longer hosts container 308 c. Instead,the edge site 306 c-2 hosts the container 308 c. Prefix 318 c enters thecloud-computing system 300 c at the edge site 306 c-2. The container 308c still provides services to a device behind the prefix 318 c.

At time t₂, the service 310 c may again query the edge sites 306 c-1,306 c-2 for information regarding containers hosted on the edge sites306 c-1, 306 c-2. The service 310 c may query the edge site 306 c-1 toprovide information regarding any containers hosted on the edge site 306c-1. The edge site 306 c-1 may respond that it is not hosting anycontainers. In contrast, the edge site 306 c-2 may indicate that ithosts the container 308 c and provide information identifying thecontainer 308 c, such as a GUI for the container 308 c. The edge site306 c-2 may also indicate that the container 308 c provides services tothe prefix 318 c. The edge site 306 c-2 may indicate that traffic fromthe prefix 318 c enters the cloud-computing system 300 c through theedge site 306 c-2. The service 310 c may store the informationidentifying the container 308 c, the prefix 318 c, a prefix-connectionlocation for the prefix 318 c (the edge site 306 c-2), and a containerlocation of the container 308 c (the edge site 306 c-2) as a record 320c.

The service 310 c may determine whether to move the container 308 c. Theservice 310 c may compare the prefix-connection location associated withthe container 308 c with the prefix-connection location associated withthe container 308 b. The service 310 c may compare the prefix-connectionlocation shown in the record 320 c with the prefix-connection locationshown in the record 320 b. The service 310 c may determine that theprefix-connection location shown in the record 320 c is identical to theprefix-connection location shown in the record 320 b. In response tothat observation, the service 310 c may determine to not move thecontainer 308 c.

In the alternative, the service 310 c may compare the container locationof the container 308 c in the record 320 c with the prefix-connectionlocation shown in the record 320 c. The service 310 c may determine thatthe prefix-connection location shown in the record 320 c is identical tothe container location shown in the record 320 c. In response to thatobservation, the service may determine to not move the container 308 c.

FIG. 4 illustrates an example method 400 for migrating containers in acloud-computing system.

The method 400 may include deploying 402 a container at a locationwithin a cloud-computing system. The container may be deployed at a datacenter within the cloud-computing system. The container may be deployedat an edge site within the cloud-computing system. The container may bedeployed at a server near the edge site and outside the data center. Thecontainer may be deployed to provide services or content to a particularuser.

The location may be deployed at a location that minimizes latencyexperienced by the user. The location may be based on where the user islocated. The location may be based on where traffic from the user entersthe cloud-computing system. The location may be where the traffic fromthe user enters the cloud-computing system. For example, if the trafficfrom the user enters the cloud-computing system at an edge site, thelocation may be the edge site. In the alternative, the location may benear where the traffic from the user enters the cloud-computing system.For example, the traffic from the user may enter the cloud-computingsystem at an edge site. But the edge site may not have capacity for thecontainer. In that case, the container may be placed at a location nearthe edge site that has capacity.

The method 400 may include detecting 404 a change in a connectionlocation where traffic serviced by the container enters thecloud-computing system. Detecting 404 the change in the connectionlocation where the traffic serviced by the container enters thecloud-computing system may include detecting, at a first time, that thetraffic enters the cloud-computing system at a first location anddetecting, at a second time, that the traffic enters the cloud-computingsystem at a second location different from the first location. The firstlocation and the second location may be edge sites within thecloud-computing system. Detecting, at the first time, that the trafficenters the cloud-computing system at the first location may includequerying the first location and receiving, from the first location,information indicating that the first location receives the traffic.Detecting, at the second time, that the traffic enters thecloud-computing system at the second location may include querying thefirst location, querying the second location, and receiving, from thesecond location, information indicating that the first location receivesthe traffic.

The method 400 may include migrating 406 the container to a new locationbased on the change in the connection location. The new location may bewithin the cloud-computing system. The new location may be where thetraffic serviced by the container enters the cloud-computing systemafter the change in the connection location. The new location may be alocation near where the traffic serviced by the container enters thecloud-computing system. The new location may be a location closer towhere the traffic serviced by the container enters the cloud-computingsystem than a previous location of the container. The new location maybe based on minimizing latency experienced by the user.

FIG. 5 illustrates an example method 500 for determining whether tomodify a location of a container in a cloud-computing system.

The method 500 may include determining 502 a prefix for which acontainer hosted on an edge site of a cloud-computing system providesservices. Determining 502 the prefix may include querying the edge siteand receiving, from the edge site, information indicating the prefix forwhich the container provides services. A service hosted in thecloud-computing system may query the edge site. The service may querythe edge site at predetermined intervals. The service may query the edgesite at non-fixed, variable intervals. The service may query the edgesite in response to user feedback, such as complaints about latency andperformance.

The method 500 may include determining 504, at a first time, a firstprefix-connection location of the prefix. The first prefix-connectionlocation of the prefix may be a location within the cloud-computingsystem where traffic from the prefix enters the cloud-computing systemat the first time. Determining 504 the first prefix-connection locationmay include querying the edge site and receiving, from the edge site,information that traffic from the prefix enters the cloud-computingsystem at the edge site. The first prefix-connection location may be theedge site that hosts the container.

The method 500 may include associating 506 the container, the prefix,and the first prefix-connection location in a record. Associating 506the container may include associating a GUI of the container.Associating 506 may include storing the record within thecloud-computing system.

The method 500 may include determining 508, at a second time, a secondprefix-connection location of the prefix. The second prefix-connectionlocation of the prefix may be a location within the cloud-computingsystem where traffic from the prefix enters the cloud-computing systemat the second time. Determining 508 the second prefix-connectionlocation may include querying the edge site and receiving, from the edgesite, information that traffic from the prefix enters thecloud-computing system at the edge site. In the alternative, determining508 the second prefix-connection location may include querying a secondedge site and receiving, from the edge site, information that trafficfrom the prefix enters the cloud-computing system at the second edgesite. The cloud-computing system may include a data center and the firstprefix-connection location and the second prefix-connection location maynot be included in the data center.

The method 500 may include comparing 510, the second prefix-connectionlocation with the first prefix-connection location. Comparing 510 thesecond prefix-connection location with the first prefix-connectionlocation may include determining that the second prefix-connectionlocation is different from the first prefix-connection location. In thealternative, comparing 510 the second prefix-connection location withthe first prefix-connection location may include determining that thesecond prefix-connection location is identical to the firstprefix-connection location.

The method 500 may include determining 512 whether to move the containerbased on the comparison of the second prefix-connection location withthe first prefix-connection location.

Determining 512 whether to move the container may include determining tomove the container when the second prefix-connection location isdifferent from the first prefix-connection location. In that case, themethod 500 may further include migrating the container to the secondprefix-connection location or a location within the cloud-computingsystem closer to the second prefix-connection location than the edgesite.

Determining 512 whether to move the container may include determining tonot move the container when the second prefix-connection location isidentical to the first prefix-connection location. In that case, themethod 500 may further include maintaining the container at the edgesite.

FIG. 6 illustrates an example method 600 for migrating a container in acloud-computing system.

The method 600 may include receiving 602 a request to deploy a computecontainer to provide services to a prefix. A user behind the prefix mayrequest services from a cloud-computing system. The user's request forservices may be the request to deploy the compute container. The computecontainer may provide services to the user.

The method 600 may include determining 604 a prefix-connection locationof the prefix. The prefix-connection location of the prefix may be alocation within the cloud-computing system where traffic from the prefixenters the cloud-computing system. The prefix-connection location may bean edge site of the cloud-computing system. The prefix-connectionlocation may be an edge site near the user. The prefix-connectionlocation may be an edge site far from the user. The prefix-connectionlocation may be a data center within the cloud-computing system.Determining 604 the prefix-connection location of the prefix may occurat a first time.

The method 600 may include deploying 606 the compute container based onthe prefix-connection location. Deploying 606 the compute containerbased on the prefix-connection location may include deploying thecompute container at the prefix-connection location. The cloud-computingsystem may deploy the compute container to minimize latency experiencedby the user.

The method 600 may include determining 608 a second prefix-connectionlocation of the prefix. The second prefix-connection location of theprefix may be a location within the cloud-computing system where trafficfrom the prefix enters the cloud-computing system. The secondprefix-connection location may be an edge site of the cloud-computingsystem. Determining 604 the second prefix-connection location of theprefix may occur at a second time after the first time.

The method 600 may include determining 610 that the secondprefix-connection location is different from the prefix-connectionlocation.

The method 600 may include migrating 612 the compute container based onthe second prefix-connection location. Migrating 612 the computecontainer based on the second prefix-connection location may includemigrating the compute container to the second prefix-connectionlocation. The cloud-computing system may migrate the compute containerto minimize latency experienced by the user.

FIG. 7 illustrates an example method 700 for sending messages to acloud-computing system.

The method 700 may include sending 702 a first message to acloud-computing system, wherein the first message enters thecloud-computing system at a first location that hosts a containerservicing a user device. The user device may send 702 the first messageto the cloud-computing system.

The method 700 may include sending 704 a second message to thecloud-computing system, wherein the second message enters thecloud-computing system at a second location that is different from thefirst location and the second location does not host the container. Theuser device may send 704 the second message to the cloud-computingsystem.

The method 700 may include sending 706 a third message to thecloud-computing system, wherein the third message enters thecloud-computing system at the second location and the second locationhosts the container. The user device may send 706 the third message tothe cloud-computing system. The second message may take longer to reachthe first location than the third message takes to reach the secondlocation.

FIG. 8 illustrates certain components that may be included within acomputer system 800. One or more computer systems 800 may be used toimplement the various devices, components, and systems described herein.

The computer system 800 includes a processor 801. The processor 801 maybe a general purpose single- or multi-chip microprocessor (e.g., anAdvanced RISC (Reduced Instruction Set Computer) Machine (ARM)), aspecial purpose microprocessor (e.g., a digital signal processor (DSP)),a microcontroller, a programmable gate array, etc. The processor 801 maybe referred to as a central processing unit (CPU). Although just asingle processor 801 is shown in the computer system 800 of FIG. 8 , inan alternative configuration, a combination of processors (e.g., an ARMand DSP) could be used.

The computer system 800 also includes memory 803 in electroniccommunication with the processor 801. The memory 803 may be anyelectronic component capable of storing electronic information. Forexample, the memory 803 may be embodied as random access memory (RAM),read-only memory (ROM), magnetic disk storage media, optical storagemedia, flash memory devices in RAM, on-board memory included with theprocessor, erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM) memory, registers, andso forth, including combinations thereof.

Instructions 805 and data 807 may be stored in the memory 803. Theinstructions 805 may be executable by the processor 801 to implementsome or all of the functionality disclosed herein. Executing theinstructions 805 may involve the use of the data 807 that is stored inthe memory 803. Any of the various examples of modules, components,packages, applications, and operating systems described herein may beimplemented, partially or wholly, as instructions 805 stored in memory803 and executed by the processor 801. Any of the various examples ofdata described herein may be among the data 807 that is stored in memory803 and used during execution of the instructions 805 by the processor801.

A computer system 800 may also include one or more communicationinterfaces 809 for communicating with other electronic devices. Thecommunication interface(s) 809 may be based on wired communicationtechnology, wireless communication technology, or both. Some examples ofcommunication interfaces 809 include a Universal Serial Bus (USB), anEthernet adapter, a wireless adapter that operates in accordance with anInstitute of Electrical and Electronics Engineers (IEEE) 802.11 wirelesscommunication protocol, a Bluetooth® wireless communication adapter, andan infrared (IR) communication port.

A computer system 800 may also include one or more input devices 811 andone or more output devices 813. Some examples of input devices 811include a keyboard, mouse, microphone, remote control device, button,joystick, trackball, touchpad, and lightpen. Some examples of outputdevices 813 include a speaker and a printer. One specific type of outputdevice that is typically included in a computer system 800 is a displaydevice 815. Display devices 815 used with embodiments disclosed hereinmay utilize any suitable image projection technology, such as liquidcrystal display (LCD), light-emitting diode (LED), gas plasma,electroluminescence, or the like. A display controller 817 may also beprovided, for converting data 807 stored in the memory 803 into text,graphics, and/or moving images (as appropriate) shown on the displaydevice 815.

The various components of the computer system 800 may be coupledtogether by one or more buses, which may include a power bus, a controlsignal bus, a status signal bus, a data bus, etc. For the sake ofclarity, the various buses are illustrated in FIG. 8 as a bus system819.

The techniques disclosed herein can be implemented in hardware,software, firmware, or any combination thereof, unless specificallydescribed as being implemented in a specific manner. Any featuresdescribed as modules, components, or the like can also be implementedtogether in an integrated logic device or separately as discrete butinteroperable logic devices. If implemented in software, the techniquescan be realized at least in part by a non-transitory computer-readablemedium having computer-executable instructions stored thereon that, whenexecuted by at least one processor, perform some or all of the steps,operations, actions, or other functionality disclosed herein. Theinstructions can be organized into routines, programs, objects,components, data structures, etc., which can perform particular tasksand/or implement particular data types, and which can be combined ordistributed as desired in various embodiments.

As used in the present disclosure, a “cloud-computing system” may referto a network of connected computing devices that provide variousservices to client devices. For example, a distributed computing systemmay include a collection of physical server devices (such as servernodes) organized in a hierarchical structure. Such a hierarchicalstructure may include computing zones, clusters, virtual local areanetworks (VLANs), racks, fault domains, etc. One or more specificexamples and implementations described herein may relate specifically to“data centers” that include multiple server nodes. But the features andfunctionality described in connection with one or more node data centersmay similarly relate to racks, fault domains, or other hierarchicalstructures of physical server devices. The cloud computing system mayrefer to a private or public cloud computing system.

As used in the present disclosure, a “computing container,” “virtualcontainer,” “compute container,” or “container” may refer to a virtualservice or layer on a server node of a cloud computing system thatprovides access to computing resources (such as a storage space) and/ora software application hosted by the cloud-computing system. Computingcontainers may provide services to any number of containerizedapplications on a cloud-computing system. As used in the presentdisclosure, a “virtual service” or a “service” may refer to a serviceprovided by a cloud-computing system.

A “virtual machine” may refer to an emulation of a computer system on aserver node that provides functionality of one or more applications onthe cloud computing system. Virtual machines may provide functionalityneeded to execute one or more operating systems. In addition, virtualmachines may make use of hypervisors on processors of server devicesthat support virtual replication of hardware. While one or more specificexamples and implementations described herein may relate specifically tovirtual machines, features and functionality described in connectionwith utilizing resources on a server node may similarly apply to othertypes of computing containers.

The term “processor” can refer to a general purpose single- ormulti-chip microprocessor (e.g., an Advanced RISC (Reduced InstructionSet Computer) Machine (ARM)), a special purpose microprocessor (e.g., adigital signal processor (DSP)), a microcontroller, a programmable gatearray, or the like. A processor can be a central processing unit (CPU).In some embodiments, a combination of processors (e.g., an ARM and DSP)could be used to implement some or all of the techniques disclosedherein.

The term “memory” can refer to any electronic component capable ofstoring electronic information. For example, memory may be embodied asrandom access memory (RAM), read-only memory (ROM), magnetic diskstorage media, optical storage media, flash memory devices in RAM,on-board memory included with a processor, erasable programmableread-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM) memory, registers, and so forth, including combinationsthereof.

The steps, operations, and/or actions of the methods described hereinmay be interchanged with one another without departing from the scope ofthe claims. In other words, unless a specific order of steps,operations, and/or actions is required for proper functioning of themethod that is being described, the order and/or use of specific steps,operations, and/or actions may be modified without departing from thescope of the claims.

The term “determining” (and grammatical variants thereof) can encompassa wide variety of actions. For example, “determining” can includecalculating, computing, processing, deriving, investigating, looking up(e.g., looking up in a table, a database or another data structure),ascertaining and the like. Also, “determining” can include receiving(e.g., receiving information), accessing (e.g., accessing data in amemory) and the like. Also, “determining” can include resolving,selecting, choosing, establishing and the like.

The terms “comprising,” “including,” and “having” are intended to beinclusive and mean that there can be additional elements other than thelisted elements. Additionally, it should be understood that referencesto “one embodiment” or “an embodiment” of the present disclosure are notintended to be interpreted as excluding the existence of additionalembodiments that also incorporate the recited features. For example, anyelement or feature described in relation to an embodiment herein may becombinable with any element or feature of any other embodiment describedherein, where compatible.

The present disclosure may be embodied in other specific forms withoutdeparting from its spirit or characteristics. The described embodimentsare to be considered as illustrative and not restrictive. The scope ofthe disclosure is, therefore, indicated by the appended claims ratherthan by the foregoing description. Changes that come within the meaningand range of equivalency of the claims are to be embraced within theirscope.

What is claimed is:
 1. A method implemented at a computer system thatincludes a processor comprising: receiving a request to deploy a computecontainer to provide services to a prefix; determining a firstprefix-connection location of the prefix; deploying the computecontainer based on the first prefix-connection location; determining asecond prefix-connection location of the prefix; determining that thesecond prefix-connection location is different from the firstprefix-connection location; and migrating the compute container based onthe second prefix-connection location.
 2. The method of claim 1, whereinthe request to deploy the compute container is received from a userdevice that is behind the prefix.
 3. The method of claim 1, wherein therequest is a request for services received from a user device.
 4. Themethod of claim 1, wherein, the first prefix-connection location is afirst location within a cloud-computing system where traffic from theprefix enters the cloud-computing system at a first time, and the secondprefix-connection location is a second location within thecloud-computing system where traffic from the prefix enters thecloud-computing system at a second time after the first time.
 5. Themethod of claim 4, wherein the first prefix-connection location or thesecond prefix-connection location is an edge site of the cloud-computingsystem.
 6. The method of claim 4, wherein the first prefix-connectionlocation or the second prefix-connection location is a data centerwithin the cloud-computing system.
 7. The method of claim 1, wherein,deploying the compute container based on the first prefix-connectionlocation comprises deploying the compute container at the firstprefix-connection location, and migrating the compute container based onthe second prefix-connection location comprises migrating the computecontainer to the second prefix-connection location.
 8. The method ofclaim 7, wherein, deploying the compute container at the firstprefix-connection location is performed to minimize a first latencyexperienced by a user device at a first time, and migrating the computecontainer to the second prefix-connection location is performed tominimize a second latency experienced by the user device at a secondtime after the first time.
 9. The method of claim 1, wherein,determining the first prefix-connection location of the prefix occurs ata first time, and determining the second prefix-connection location ofthe prefix occurs at a second time after the first time.
 10. A system,comprising: a processor; a memory in electronic communication with theprocessor; and instructions stored in the memory, the instructions beingexecutable by the processor to: receive a request to deploy a computecontainer to provide services to a prefix; determine a firstprefix-connection location of the prefix, where traffic from the prefixenters a cloud-computing system at a first time; deploy the computecontainer based on the first prefix-connection location; determine asecond prefix-connection location of the prefix, where traffic from theprefix enters the cloud-computing system at a second time after thefirst time; determine that the second prefix-connection location isdifferent from the first prefix-connection location; and migrate thecompute container based on the second prefix-connection location. 11.The system of claim 10, wherein the request to deploy the computecontainer is received from a user device that is behind the prefix. 12.The system of claim 10, wherein the request is a request for servicesreceived from a user device.
 13. The system of claim 10, wherein thefirst prefix-connection location or the second prefix-connectionlocation is an edge site of the cloud-computing system.
 14. The systemof claim 10, wherein the first prefix-connection location or the secondprefix-connection location is a data center within the cloud-computingsystem.
 15. The system of claim 10, wherein, deploying the computecontainer based on the first prefix-connection location comprisesdeploying the compute container at the first prefix-connection location,and migrating the compute container based on the secondprefix-connection location comprises migrating the compute container tothe second prefix-connection location.
 16. The system of claim 15,wherein, deploying the compute container at the first prefix-connectionlocation is performed to minimize a first latency experienced by a userdevice at the first time, and migrating the compute container to thesecond prefix-connection location is performed to minimize a secondlatency experienced by the user device at the second time.
 17. Acomputer-readable storage medium comprising instructions that areexecutable by a processor to cause a computer system to: receive arequest to deploy a compute container to provide services to a prefix;determine a first prefix-connection location of the prefix, wheretraffic from the prefix enters a cloud-computing system at a first time;deploy the compute container based on the first prefix-connectionlocation; determine a second prefix-connection location of the prefix,where traffic from the prefix enters the cloud-computing system at asecond time after the first time; determine that the secondprefix-connection location is different from the first prefix-connectionlocation; and migrate the compute container based on the secondprefix-connection location.
 18. The computer-readable storage medium ofclaim 17, wherein, the request to deploy the compute container isreceived from a user device that is behind the prefix, and the requestis a request for services.
 19. The computer-readable storage medium ofclaim 17, wherein the first prefix-connection location or the secondprefix-connection location is an edge site of the cloud-computing systemor a data center within the cloud-computing system.
 20. Thecomputer-readable storage medium of claim 17, wherein, deploying thecompute container based on the first prefix-connection locationcomprises deploying the compute container at the first prefix-connectionlocation to minimize a first latency experienced by a user device at thefirst time, and migrating the compute container based on the secondprefix-connection location comprises migrating the compute container tothe second prefix-connection location to minimize a second latencyexperienced by the user device at the second time.